Description

This PR is the final step in implementing the panic expression and the ABI errors, as defined in the ABI Errors RFC.

The PR generates the errorCodes section in the ABI, like, e.g.:

"errorCodes": {
  "18446744069414584320": {
    "pos": {
      "pkg": "my_lib@1.2.3",
      "file": "src/lib.rs",
      "line": 42,
      "column": 13
    },
    "logId": null,
    "msg": "Error message."
  },
  "18446744069414584321": {
    "pos": {
      "pkg": "my_contract",
      "file": "src/main.rs",
      "line": 21,
      "column": 34
    },
    "logId": "4933727799282657266",
    "msg": null
  }
}

If the panic argument is a string slice that can be const-evaluated, the msg field of the corresponding error code is generated, and a log is not emitted. The string itself is stored only within the ABI JSON, and is not included into the generated bytecode.

Additionally, the PR:

• provides a common infrastructure for obtaining a SourceLocation from a Span. This is currently used in the implementation of the __dbg intrinsics and the panic expression.
• improves filtering of forc outputs in snapshot tests by supporting regular expressions. The grep command is renamed to regex to avoid confusion with piping the actual grep CLI command.

Partially addresses #6765.

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.